Custom Hook Parameters
The custom hook parameters that should be passed are determined by the parameters supported in the custom hook tool.
The following table provides information on the supported parameters.
Parameter | Description |
---|---|
paramfile=<XML Path and file name> |
When this parameter is included, Cobra will output the XML parameters used by the process into the file specified. The path and file name are then passed as a parameter to the custom hook tool. When running Cobra in an n-tier deployment, the XML file is created on the server using the path specified. For example, if c:\temp\temp.xml is specified as the paramfile value, this is created on the C: drive of the server. Note: The parameter output currently does not include the connection information. This information is cleared out before being stored in the specified XML file.
|
Executable Custom Hook Tool
When paramfile is specified, the value (path/location) is passed as a parameter to the exe file so that the custom tool should accept at least one string parameter.
Visual FoxPro Procedure (VFP) Custom Hook Tool
The VFP custom hook tool will have to read the parameter file directly if it needs information. The custom process passes the process object as the first parameter to the custom hook tool. There is an optional second parameter for the success result if the process returns a result.